| 1. | I ' ll try my best to answer your question in the next thread
我会尽我所能在下一个议题中回答?的问题。 |
| 2. | Is thrown in the next thread that acquires the mutex
Net framework 2 . 0版中，获取该mutex的下一个线程中将引发 |
| 3. | Releases the lock , the next thread in the ready queue acquires the lock
的线程释放锁后，就绪队列中的下一个线程将获取该锁。 |
| 4. | At this point , the next thread in the ready queue if there is one is allowed to take control of the lock
此时，允许就绪队列中的下一个线程（如果有）控制锁。 |
| 5. | The next thread in the object s ready queue if there is one acquires the lock and has exclusive use of the object
对象的就绪队列中的下一个线程（如果有）获取锁并拥有对对象的独占使用。 |
| 6. | If a deadlock has just been detected , it is assumed that the next threads that must wait for a lock are entering the deadlock cycle
如果刚刚检测到死锁，则假定必须等待锁的下一个线程正进入死锁循环。 |
| 7. | The next thread to request ownership of the mutex can handle this exception and proceed if the integrity of the data structures can be verified
如果可以验证这些数据结构的完整性，那么下一个请求mutex所有权的线程就可以处理此异常并继续运行。 |
| 8. | When the system switches from one thread to another , it saves the thread context of the preempted thread and reloads the saved thread context of the next thread in the thread queue
当系统从一个线程切换到另一个线程时，它将保存被抢先的线程的线程上下文，并重新加载线程队列中下一个线程的已保存线程上下文。 |
